fix: Initialize logging for crashpad #26267
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![trop[bot]](https://avatars.githubusercontent.com/in/9879?s=60&v=4){kind=small}
5 tasks
zcbenz
requested changes
Nov 2, 2020
codebytere
force-pushed
the
trop/9-x-y-bp-fix-initialize-logging-for-crashpad-1604013851307
branch
from
064517b
to
2291e54
Compare
zcbenz
approved these changes
Nov 10, 2020
jkleinsc
approved these changes
Nov 10, 2020
|
Release Notes Persisted
|
jkleinsc
deleted the
trop/9-x-y-bp-fix-initialize-logging-for-crashpad-1604013851307
branch
This was referenced Mar 7, 2021
This was referenced Mar 14, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #26250
See that PR for details.
Notes: fix debug.log files being created under working directory on windows